Managing the Cluster service from the command line

You can use cluster service commands to troubleshoot or debug the Cluster service from the command prompt. The Cluster service command line can only be run locally from the cluster directory:

%systemroot%\cluster

Do not use the clussvc command under normal conditions, but only as a temporary diagnostic tool if the Cluster service fails to start (because of a system-related error, for example).

Important

If you use the clussvc command to start the Cluster service in a server cluster with 3 or more nodes, the Cluster service will be unable to authenticate any intracluster messages sent in multicast mode. The intracluster traffic in the server cluster will then revert to unicast mode. However, this will not affect the ability of any node to participate in the server cluster. For information, see Network communication between nodes.
Do not change the Cluster service account password while running the Cluster service from the command line. For information on changing the Cluster service account password, see To change the Cluster service account password

For information about other command-line utilities, see Command-line reference. For more information about manageability, see Understanding Windows Management.

The following rules apply when entering commands from the command prompt:

When entering commands from the command prompt, you can specify multiple options for one command line. Clussvc.exe processes options from left to right. If an option fails, the command stops running at the failed option.
To use the Cluster service commands, you must be logged on with administrative rights.
To stop the Cluster service, at the command prompt, press CTRL+C.

The command line for starting the Cluster service has the following syntax:

clussvc /debug [command]

The Cluster service runs in the command prompt window and displays all output recorded in the cluster log in the window.

Cluster service command	Shortcut command	Action
/debugresmon	/DR	Enables the debugging of the resource dynamic-link libraries (DLLs) that are loaded by the resource monitor process.
/fixquorum	/FQ	Allows the Cluster service to start up, despite problems with the quorum device.
/resetquorumlog	/RQ	If the quorum log file is not found or is corrupted, creates a new quorum log file based on information in the local node's cluster database file. If the quorum log file is found and is not corrupted, this command has no effect.
/norepevtlogging	n/a	Allows no replication of event log entries.
/forcequorum	/FO	Restores quorum for a majority node set server cluster that has lost quorum. Note It is recommended that you use the method described in To force quorum in a majority node set server cluster instead of the clussvc /debug /forcequorum command option described here.

For more information on commands for the Cluster service, see: